..
    This file was autogenerated via Documentation/update-codeowners.sh, do not edit manually

Code owners are used by the Cilium community to consolidate common knowledge
into teams that can provide consistent and actionable feedback to
contributors. This section will describe groups of teams and suggestions
about the focus areas for review.

The primary motivation for these teams is to provide structure around review
processes to ensure that contributors know how to reach out to community
members to conduct discussions, ensure contributions meet the expectations of
the community, and align on the direction of proposed changes. Furthermore,
while these teams are primarily drawn upon to provide review on specific pull
requests, they are also encouraged to self-organize around how to make
improvements to their areas of the Cilium project over time.

Any committer may self-nominate to code owner teams. Reach out to the core
team on the #committers channel in Slack to coordinate. Committers do not
require expert knowledge in an area in order to join a code owner team,
only a willingness to engage in discussions and learn about the area.

Project-wide
++++++++++++

These code owners may provide feedback for Pull Requests submitted to any
repository in the Cilium project:

- `@cilium/api <https://github.com/orgs/cilium/teams/api>`__:
  Ensure the backwards-compatibility of Cilium REST and gRPC APIs, excluding
  Hubble which is owned by `@cilium/sig-hubble-api <https://github.com/orgs/cilium/teams/sig-hubble-api>`__.
- `@cilium/build <https://github.com/orgs/cilium/teams/build>`__:
  Provide feedback on languages and scripting used for build and packaging
  system: Make, Shell, Docker.
- `@cilium/cli <https://github.com/orgs/cilium/teams/cli>`__:
  Provide user experience feedback on changes to Command-Line Interfaces.
  These owners are a stand-in for the user community to bring a user
  perspective to the review process. Consider how information is presented,
  consistency of flags and options.
- `@cilium/ci-structure <https://github.com/orgs/cilium/teams/ci-structure>`__:
  Provide guidance around the best use of Cilium project continuous
  integration and testing infrastructure, including GitHub actions, VM
  helpers, testing frameworks, etc.
- `@cilium/community <https://github.com/orgs/cilium/teams/community>`__:
  Maintain files that refer to Cilium community users such as USERS.md.
- `@cilium/contributing <https://github.com/orgs/cilium/teams/contributing>`__:
  Encourage practices that ensure an inclusive contributor community. Review
  tooling and scripts used by contributors.
- `@cilium/docs-structure <https://github.com/orgs/cilium/teams/docs-structure>`__:
  Ensure the consistency and layout of documentation. General feedback on the
  use of Sphinx, how to communicate content clearly to the community. This
  code owner is not expected to validate the technical correctness of
  submissions. Correctness is typically handled by another code owner group
  which is also assigned to any given piece of documentation.
- `@cilium/sig-foundations <https://github.com/orgs/cilium/teams/sig-foundations>`__:
  Review changes to the core libraries and provide guidance to overall
  software architecture.
- `@cilium/github-sec <https://github.com/orgs/cilium/teams/github-sec>`__:
  Responsible for maintaining the security of repositories in the Cilium
  project by maintaining best practices for workflow usage, for instance
  preventing malicious use of GitHub actions.
- `@cilium/helm <https://github.com/orgs/cilium/teams/helm>`__:
  Provide input on the way that Helm can be used to configure features. These
  owners are a stand-in for the user community to bring a user perspective to
  the review process. Ensure that Helm changes are defined in manners that
  will be forward-compatible for upgrade and follow best practices for
  deployment (for example, being GitOps-friendly).
- `@cilium/sig-hubble-api <https://github.com/orgs/cilium/teams/sig-hubble-api>`__:
  Review all Hubble API related changes. The Hubble API covers gRPC and
  metrics endpoints. The team ensures that API changes are backward
  compatible or that a new API version is created for backward incompatible
  changes.
- `@cilium/metrics <https://github.com/orgs/cilium/teams/metrics>`__:
  Provide recommendations about the types, names and labels for metrics to
  follow best practices. This includes considering the cardinality impact of
  metrics being added or extended.
- `@cilium/security <https://github.com/orgs/cilium/teams/security>`__:
  Provide feedback on changes that could have security implications for Cilium,
  and maintain security-related documentation.
- `@cilium/tophat <https://github.com/orgs/cilium/teams/tophat>`__:
  Top Hat duties rotate between the committer group from week to week, and
  they may assist in maintenance, triage and backporting duties across
  different Cilium repositories. Catch-all for code not otherwise owned by a
  team.
- `@cilium/vendor <https://github.com/orgs/cilium/teams/vendor>`__:
  Review vendor updates for software dependencies to check for any potential
  upstream breakages / incompatibilities. Discourage the use of unofficial
  forks of upstream libraries if they are actively maintained.

Repository Owners
+++++++++++++++++

The following code owners are responsible for a range of general feedback for
contributions to specific repositories:

- `@cilium/sig-hubble <https://github.com/orgs/cilium/teams/sig-hubble>`__:
  Review all Cilium and Hubble code related to observing system events,
  exporting those via gRPC protocols outside the node and outside the
  cluster. those event channels, for example via TLS.
- `@cilium/hubble-ui <https://github.com/orgs/cilium/teams/hubble-ui>`__:
  Maintain the Hubble UI graphical interface.
- `@cilium/tetragon <https://github.com/orgs/cilium/teams/tetragon>`__:
  Review of all Tetragon code, both for Go and C (for eBPF).

The teams above are responsible for reviewing the majority of contributions
to the corresponding repositories. Additionally, there are "maintainer" teams
listed below which may not be responsible for overall code review for a
repository, but they have administrator access to the repositories and so
they can assist with configuring GitHub repository settings, secrets, and
related processes. For the full codeowners for individual repositories, see
the CODEOWNERS file in the corresponding repository.

- `@cilium/cilium-cli-maintainers <https://github.com/orgs/cilium/teams/cilium-cli-maintainers>`__
- `@cilium/cilium-maintainers <https://github.com/orgs/cilium/teams/cilium-maintainers>`__
- `@cilium/cilium-packer-ci-build-maintainers <https://github.com/orgs/cilium/teams/cilium-packer-ci-build-maintainers>`__
- `@cilium/ebpf-lib-maintainers <https://github.com/orgs/cilium/teams/ebpf-lib-maintainers>`__
- `@cilium/hubble-maintainers <https://github.com/orgs/cilium/teams/hubble-maintainers>`__
- `@cilium/image-tools-maintainers <https://github.com/orgs/cilium/teams/image-tools-maintainers>`__
- `@cilium/metallb-maintainers <https://github.com/orgs/cilium/teams/metallb-maintainers>`__
- `@cilium/openshift-terraform-maintainers <https://github.com/orgs/cilium/teams/openshift-terraform-maintainers>`__
- `@cilium/proxy-maintainers <https://github.com/orgs/cilium/teams/proxy-maintainers>`__
- `@cilium/tetragon-maintainers <https://github.com/orgs/cilium/teams/tetragon-maintainers>`__

Cloud Integrations
++++++++++++++++++

The following codeowner groups provide insight into the integrations with
specific cloud providers:

- `@cilium/alibabacloud <https://github.com/orgs/cilium/teams/alibabacloud>`__
- `@cilium/aws <https://github.com/orgs/cilium/teams/aws>`__
- `@cilium/azure <https://github.com/orgs/cilium/teams/azure>`__

Cilium Internals
++++++++++++++++

The following codeowner groups cover more specific knowledge about Cilium
Agent internals or the way that particular Cilium features interact with
external software and protocols:

- `@cilium/docker <https://github.com/orgs/cilium/teams/docker>`__:
  Maintain the deprecated docker-plugin.
- `@cilium/endpoint <https://github.com/orgs/cilium/teams/endpoint>`__:
  Provide background on how the Cilium Endpoint package fits into the overall
  agent architecture, relationship with generation of policy / datapath
  constructs, serialization and restore from disk.
- `@cilium/envoy <https://github.com/orgs/cilium/teams/envoy>`__:
  Maintain the L7 proxy integration with Envoy. This includes the
  configurations for Envoy via xDS protocols as well as the extensible
  proxylib framework for Go-based layer 7 filters.
- `@cilium/egress-gateway <https://github.com/orgs/cilium/teams/egress-gateway>`__:
  Maintain the egress gateway control plane and datapath logic.
- `@cilium/fqdn <https://github.com/orgs/cilium/teams/fqdn>`__:
  Maintain the L7 DNS proxy integration.
- `@cilium/ipcache <https://github.com/orgs/cilium/teams/ipcache>`__:
  Provide background on how the userspace IPCache structure fits into the
  overall agent architecture, ordering constraints with respect to network
  policies and encryption. Handle the relationship between Kubernetes state
  and datapath state as it pertains to remote peers.
- `@cilium/ipsec <https://github.com/orgs/cilium/teams/ipsec>`__:
  Maintain the kernel IPsec configuration and related eBPF logic to ensure
  traffic is correctly encrypted.
- `@cilium/kvstore <https://github.com/orgs/cilium/teams/kvstore>`__:
  Review Cilium interactions with key-value stores, particularly etcd.
  Understand the client libraries used by Cilium for sharing state between
  nodes and clusters.
- `@cilium/loader <https://github.com/orgs/cilium/teams/loader>`__:
  Maintain the tooling that allows eBPF programs to be loaded into the
  kernel: LLVM, bpftool, use of cilium/ebpf for loading programs in the
  agent, ELF templating, etc.
- `@cilium/operator <https://github.com/orgs/cilium/teams/operator>`__:
  Review operations that occur once per cluster via the Cilium Operator
  component. Take care of the corresponding garbage collection and leader
  election logic.
- `@cilium/proxy <https://github.com/orgs/cilium/teams/proxy>`__:
  Review low-level implementations used to redirect L7 traffic to the actual
  proxy implementations (FQDN, Envoy, ...).
- `@cilium/sig-agent <https://github.com/orgs/cilium/teams/sig-agent>`__:
  Provide Cilium (agent) general Go review. Internal architecture, core data
  structures and daemon startup.
- `@cilium/sig-bgp <https://github.com/orgs/cilium/teams/sig-bgp>`__:
  Review changes to our BGP integration.
- `@cilium/sig-clustermesh <https://github.com/orgs/cilium/teams/sig-clustermesh>`__:
  Ensure the reliability of state sharing between clusters to ensure that
  each cluster maintains a separate fault domain.
- `@cilium/sig-datapath <https://github.com/orgs/cilium/teams/sig-datapath>`__:
  Provide feedback on all eBPF code changes, use of the kernel APIs for
  configuring the networking and socket layers. Coordination of kernel
  subsystems such as xfrm (IPsec), iptables / nftables, tc. Maintain the
  control plane layers that populate most eBPF maps; account for endianness
  and system architecture impacts on the datapath code.
- `@cilium/sig-hubble <https://github.com/orgs/cilium/teams/sig-hubble>`__:
  Review all Cilium and Hubble code related to observing system events,
  exporting those via gRPC protocols outside the node and outside the
  cluster. Ensure the security of those event channels, for example via TLS.
- `@cilium/sig-ipam <https://github.com/orgs/cilium/teams/sig-ipam>`__:
  Coordinate the implementation between all of the IP Address Management
  modes, provide awareness/insight into IP resource exhaustion and garbage
  collection concerns.
- `@cilium/sig-k8s <https://github.com/orgs/cilium/teams/sig-k8s>`__:
  Provide input on all interactions with Kubernetes, both for standard
  resources and CRDs. Ensure best practices are followed for the coordination
  of clusterwide state in order to minimize memory usage.
- `@cilium/sig-lb <https://github.com/orgs/cilium/teams/sig-lb>`__:
  Maintain the layers necessary to coordinate all load balancing
  configurations within the agent control plane, including Services,
  ClusterIP, NodePorts, Maglev, local redirect policies, and
  NAT46/NAT64.
- `@cilium/sig-policy <https://github.com/orgs/cilium/teams/sig-policy>`__:
  Ensure consistency of semantics for all network policy representations.
  Responsible for all policy logic from Kubernetes down to eBPF policymap
  entries, including all intermediate layers such as the Policy Repository,
  SelectorCache, PolicyCache, CachedSelectorPolicy, EndpointPolicy, etc.
- `@cilium/sig-scalability <https://github.com/orgs/cilium/teams/sig-scalability>`__:
  Maintain scalability and performance tests. Provide input on scalability
  and performance related changes.
- `@cilium/sig-servicemesh <https://github.com/orgs/cilium/teams/sig-servicemesh>`__:
  Provide input on the way that Service Mesh constructs such as Gateway API
  are converted into lower-level constructs backed by eBPF or Envoy
  configurations. Maintain the CRDs necessary for Service Mesh functionality.
- `@cilium/wireguard <https://github.com/orgs/cilium/teams/wireguard>`__:
  Maintain the kernel WireGuard configuration and datapath impacts related to
  ensuring traffic is encrypted correctly when WireGuard mode is enabled.
